Skip to content

Enable linting #732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 42 commits into
base: main
Choose a base branch
from
Draft

Enable linting #732

wants to merge 42 commits into from

Conversation

maxstack
Copy link

Add ansible-lint and super-linter to the Github PR workflow

maxstack added 30 commits June 17, 2025 09:52
The super-linter.env currently has the following additions that are to be addressed in the future:
VALIDATE_GITHUB_ACTIONS=false
VALIDATE_SHELL_SHFMT=false
VALIDATE_YAML=false

Most of the linting for the above has been addressed with just a single issue remaining that blocks the linter from being enabled.
@maxstack maxstack force-pushed the ci/enable-linting branch 3 times, most recently from 39c71e5 to e6e6e9c Compare August 1, 2025 23:22
@maxstack maxstack force-pushed the ci/enable-linting branch from e6e6e9c to 7ed8866 Compare August 1, 2025 23:30
@maxstack maxstack force-pushed the ci/enable-linting branch from 65e8371 to 7f8e61a Compare August 6, 2025 16:54
…oup where the name parameter was added.

Reverting to ansible.builtin.group: <args>

becasue args aren't an expected label:

groupadd: '{'name': 'grafana', 'gid': 979}' is not a valid group name
@maxstack maxstack force-pushed the ci/enable-linting branch 9 times, most recently from ca9e48a to 5206d97 Compare August 12, 2025 15:16
@maxstack maxstack force-pushed the ci/enable-linting branch 5 times, most recently from 4818da6 to e6a0847 Compare August 13, 2025 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant